Conversation
|
Awesome, @jake-bladt! Excited to test this out - it'll make a big difference to many people, and most immediately might even help @emarino13 get her new laptop dev environment set up. @jake-bladt - have you had a chance to check out the Travis CI build error? |
|
@DBNess I just looked at the Travis CI build error and will need to investigate more before I can say where it's coming from. While I work on this, @emarino13 might want to look into using nitrous.io for development. I was able to get codemontage to build and run there without running into any of these errors. |
|
Ooh great to know re: nitrous.io - thanks!
|
courte
added
contributor update wanted
enhancement
and removed
contributor update wanted
labels
3 participants
This work allows for the use of Vagrant to create and manage a VM for CodeMontage to run on in development. It creates the VM and allows the user to SSH into that VM to work with CodeMontage in console mode.
There is (a bug)[http://stackoverflow.com/questions/19124367/rails-app-on-percise32-vagrant-box-assets-get-text-file-busy-error-errnoe] with the current version of sass-rails that generates an error on many VMs including this one generated by Vagrant. Unfortunately, changing to a specific version of sass-rails either causes a conflict with the currently-used version of rails or with acts_as_gmappable.
Addressing the delicate balance among sass-rails, rails, and acts_as_gmappable is outside the scope of this issue. This PR only addresses the creation of a vagrant-based environment, not the compatibility issues among gems.